-
Notifications
You must be signed in to change notification settings - Fork 53
Basic orchestration and activity execution logs #405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
jviau
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to have more logging. Do we have plans for distributed tracing in this library directly? These specific logs are more valuable as spans, as that will capture all of the same information but in a more usable way.
No harm in having these logs as well though - but I suggest putting the log level to Debug as if spans are ever added, these would be lower importance.
…into cgillum/log-improvements
We're missing some basic execution logs in this SDK. For Azure Functions, this was okay because the Functions host and worker layer would sufficiently take care of logging. However, for standalone use, the base logging was insufficient.
This PR adds basic execution starting, completion, and failure logs for orchestrations and activities.